System and method for supporting GAN service request capability in a wireless user equipment (UE) device

ABSTRACT

In one embodiment, a scheme is disclosed for supporting wireless access network service request capability in a user equipment (UE) device that is operable in wide area cellular network (WACN) bands as well as in wireless access network bands (e.g., GAN bands and/or UMA bands). The UE device includes capability for gaining Internet Protocol (IP) connectivity with a wireless access network node (e.g., a GAN controller (GANC) or UMA network controller (UNC)). Thereafter, the UE device is operable to initiate a registration request message towards the wireless access network node, wherein the registration request message includes at least one information element pertaining to wireless access network services required by the UE device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This nonprovisional patent application claims priority based upon thefollowing prior U.S. provisional patent application(s): (i) “SYSTEM ANDMETHOD OF NETWORK SELECTION,” Application No. 60/631,457, filed Nov. 29,2004, in the name(s) of Adrian Buckley, George Baldwin Bumiller and PaulCarpenter, which is (are) hereby incorporated by reference.

This application discloses subject matter that is related to the subjectmatter of the following U.S. patent application(s): (i) “NETWORKSELECTION INVOLVING GANC REDIRECTION” (Docket No. 12613-US-PAT),Application No. ______, filed even date herewith; and (ii) “SYSTEM ANDMETHOD FOR PROVIDING OPERATOR-DIFFERENTIATED MESSAGING TO A WIRELESSUSER EQUIPMENT (UE) DEVICE” (Docket No. 12613-US-PAT1), Application No.______, filed even date herewith, which is (are) hereby incorporated byreference.

FIELD OF THE DISCLOSURE

The present patent disclosure generally relates to communicationnetworks. More particularly, and not by way of any limitation, thepresent patent application is directed to a system and method forsupporting wireless access network (AN) service request capability in auser equipment (UE) device operable in a wireless AN space that may beinterconnected to a wide area cellular network (WACN) space.

BACKGROUND

Wireless access networks have become a key element of a variety oftelecommunications network environments. As to enterprise networks, theyprovide convenient access to network resources for workers carryingportable computers and mobile handheld devices, and for guests ortemporary workers similarly equipped. They also provide a cost-effectivealternative to relocating physical Ethernet jacks in environments wherefacilities are moved or changed frequently. In addition, wireless accesspoints operable with diverse communication/computing devices arebecoming ubiquitous in public environments such as, e.g., hotels,airports, restaurants, and coffee shops. With the increase in high-speedInternet access, the use of access point(s) in the users' homes is alsoenvisioned and has started for other applications.

Concomitantly, several developments in the user equipment (UE) arena arealso taking place to take advantage of the capabilities offered bywireless access networks. Of particular interest is the integration ofcellular phones with the capability to interface with a wireless accessnetwork such as a wireless Local Area Network (WLAN). With such “dualmode” devices becoming available, it should be appreciated that someinterworking mechanism between the cellular network and WLAN would berequired so as to facilitate efficient handover of services from onetype of network to the other.

Current GAN specifications provide that a UE device (e.g., a mobilestation or MS) may register on a wide area cellular network (WACN) suchas a Public Land Mobile Network (PLMN) if it is discovered and allowedaccording to applicable 3^(rd) Generation Partnership Project (3GPP)standards. Also, the UE device may be allowed to register on a GAN undercertain circumstances where there is no WACN connectivity. Additionally,similar network connectivity behavior may be encountered whereUnlicensed Mobile Access (UMA) technologies are deployed as well.However, several important issues arise in such a scenario e.g., numberplan compatibility, service handover, emergency call routing, just toname a few, especially when connectivity to a PLMN is desired via a GANor UMA-based access network.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the present patentapplication may be had by reference to the following DetailedDescription when taken in conjunction with the accompanying drawingswherein:

FIG. 1 depicts a generalized network environment wherein an embodimentof the present patent disclosure may be practiced;

FIG. 2 depicts an exemplary embodiment of a network environment where auser equipment (UE) device is operably disposed in accordance with theteachings of the present patent disclosure;

FIG. 3 depicts a functional block diagram of a network system where awide area cellular network (WACN) such as a Public Land Mobile Network(PLMN) is accessible through a generic access network (GAN) andassociated controller (GANC);

FIG. 4A depicts an exemplary embodiment of a circuit-switched (CS)protocol stack operable with the network system shown in FIG. 3;

FIG. 4B depicts an exemplary embodiment of a packet-switched (PS)protocol stack operable with the network system shown in FIG. 3;

FIG. 5A depicts a network arrangement where an access network (GAN orWireless LAN) is operable to connect to a plurality of PLMNs accordingto one embodiment wherein each PLMN is served by a corresponding GANC;

FIG. 5B depicts a network arrangement where an access network (GAN orWireless LAN) is operable to connect to a plurality of PLMNs accordingto one embodiment wherein a plurality of virtual GANC partitions on asingle GANC are operable to serve the corresponding PLMNs;

FIG. 6 is a flowchart of a generalized network discovery and selectionscheme according to one embodiment;

FIG. 7A is a flowchart of a method of gathering network informationaccording to one embodiment for purposes of the present disclosure;

FIG. 7B is a flowchart of a GANC discovery and registration methodaccording to one embodiment wherein one or more GAN services may berequested by a wireless UE device;

FIGS. 8A and 8B are flowcharts associated with a generalized GANCselection and redirection scheme according to one embodiment;

FIG. 9 depicts a functional block diagram of an exemplary GANC/UNC nodeaccording to one embodiment; and

FIG. 10 depicts a block diagram of an embodiment of a UE device operableaccording to the teachings of the present patent disclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

The present patent disclosure is broadly directed to a scheme forsupporting wireless access network service request capability in a userequipment (UE) device that is operable in WACN bands as well as inwireless access network bands (e.g., GAN bands and/or UMA bands). The UEdevice includes capability for gaining Internet Protocol (IP)connectivity with a wireless access network node (e.g., a GAN controller(GANC) or UMA network controller (UNC)). Thereafter, the UE device isoperable to initiate a registration request message towards the wirelessaccess network node, wherein the registration request message includesat least one information element pertaining to wireless access networkservices required by the UE device.

In one aspect, an embodiment of a network messaging method is disclosedwhich comprises: gaining IP connectivity by a UE device with respect toa wireless access network node disposed in a network environment that iscomprised of a wireless access network (AN) space operable to be coupledto a WACN space; and initiating a registration request message by the UEdevice towards the wireless access network node, wherein theregistration request message includes at least one information elementpertaining to AN services required by the UE device.

In a further aspect, an embodiment of a UE device is disclosed whichcomprises: means for gaining IP connectivity with respect to a wirelessaccess network node disposed in a network environment that is comprisedof a wireless AN space operable to be coupled to a WACN space; and meansfor initiating a registration request message towards the wirelessaccess network node, wherein the registration request message includesat least one information element pertaining to AN services required bythe UE device.

In yet another aspect, an embodiment of a network system is disclosedwhich comprises: a wireless access network node disposed in a networkenvironment that is comprised of a wireless access network (AN) spaceoperable to be coupled to a WACN space, the wireless access network nodefor facilitating wireless access services with respect to a Public LandMobile Network (PLMN) of the WACN space; a UE device including means forgaining IP connectivity with the wireless access network node; and meansassociated with the UE device for initiating a registration requestmessage towards the wireless access network node, wherein theregistration request message includes at least one information elementpertaining to wireless access services required by the UE device.

A system and method of the present patent disclosure will now bedescribed with reference to various examples of how the embodiments canbest be made and used. Like reference numerals are used throughout thedescription and several views of the drawings to indicate like orcorresponding parts, wherein the various elements are not necessarilydrawn to scale. Referring now to the drawings, and more particularly toFIG. 1, depicted therein is an exemplary generalized network environment100 wherein an embodiment of the present patent disclosure may bepracticed. A user equipment (UE) device 102 may comprise any portablecomputer (e.g., laptops, palmtops, or handheld computing devices) or amobile communications device (e.g., cellular phones or data-enabledhandheld devices capable of receiving and sending messages, webbrowsing, et cetera), or any enhanced personal digital assistant (PDA)device or integrated information appliance capable of email, video mail,Internet access, corporate data access, messaging, calendaring andscheduling, information management, and the like, that is preferablyoperable in one or more modes of operation. For example, UE device 102may operate in the cellular telephony band frequencies as well aswireless Local Area Network (WLAN) bands, or possibly in the WLAN bandsalone. Further, other bands in which the UE device could operatewirelessly may comprise Wi-Max bands or one or more satellite bands.Additionally, the network environment 100 is comprised of three broadcategories of communication spaces capable of providing service to UEdevice 102. In wide area cellular network (WACN) space 104, there mayexist any number of Public Land Mobile Networks (PLMNs) that areoperable to provide cellular telephony services which may or may notinclude packet-switched data services. Depending on the coverage area(s)and whether the user is roaming, WACN space 104 can include a number ofcellular RANs, associated home networks (i.e., home PLMNs or HPLMNs) 110and visited networks (i.e., VPLMNs) 112, each with appropriateinfrastructure such as Home Location Register (HLR) nodes 115, MobileSwitching Center (MSC) nodes 116, and the like. Since the WACN space 104may also include a General Packet Radio Service (GPRS) network thatprovides a packet radio access for mobile devices using the cellularinfrastructure of a Global System for Mobile Communications (GSM)-basedcarrier network, a Serving GPRS Support Node (SGSN) 114 is exemplifiedtherein. Additionally, by way of generalization, the PLMNs of the WACNspace 104 may comprise networks selected from the group comprising oneor more Enhanced Data Rates for GSM Evolution (EDGE) networks,Integrated Digital Enhanced Networks (IDENs), Code Division MultipleAccess (CDMA) networks, Universal Mobile Telecommunications System(UMTS) networks, Universal Terrestrial Radio Access Networks (UTRANs),or any 3^(rd) Generation Partnership Project (3GPP)-compliant network(e.g., 3GPP or 3GPP2), all operating with well known frequencybandwidths and protocols.

Further, UE device 102 is operable to obtain service from an accessnetwork (AN) space 106 that is operably associated with the WACN space104. In one implementation, the AN space 106 includes one or moregeneric access networks (GANs) 118 as well as any type of WLANarrangements 120. GAN 118, described in additional detail below, isoperable to provide access services between UE device 102 and a PLMNcore network using a broadband Internet Protocol (IP)-based network.WLAN arrangements 120 provide short-range wireless connectivity to UEdevice 102 via access points (APs) or “hot spots,” and can beimplemented using a variety of standards, e.g., IEEE 802.11b, IEEE802.11a, IEEE 802.11g, HiperLan and HiperLan II standards, Wi-Maxstandard, OpenAir standard, and the Bluetooth standard. Accordingly, itis envisaged that the AN space 106 may also be inclusive of UMA-basedaccess networks that deploy UMA network controller (UNC) nodes foreffectuating seamless transitions between cellular RAN (part of the WACNspace 104) and unlicensed wireless networks.

In one embodiment, interfacing between the WACN and AN spaces may beeffectuated in accordance with certain standards. For instance, GAN 118may be interfaced with a PLMN core using the procedures set forth in the3GPP TR 43.901 and 3GPP TS 43.xxx documents as well as relateddocumentation. Likewise, WLAN 120 may interfaced with a PLMN core usingthe procedures set forth in the 3GPP TS 22.234, 3GPP TS 23.234 and 3GPPTS 24.234 documents as well as related documentation, and may thereforebe referred to as an Interworking WLAN (I-WLAN) arrangement.

Additionally, there may exist an access network (AN) space 108 notinterfaced to the WACN space 104 that offers short-range wirelessconnectivity to UE device 102. For instance, AN space 108 may compriseWLANs 122 offering non-3GPP services, such as communications over“public” access points (hotels, coffee shops, bookstores, apartmentbuildings, educational institutions, etc., whether free or for fee),enterprise access points, and visited (other enterprise) access pointswhere the user may not be a member of that enterprise but is allowed atleast some services.

Given the mosaic of the wireless network environment 100 in which UEdevice 102 may be disposed, it is desirable that a vertical handovermechanism exists such that the user can engage in a call as it movesfrom a PLMN's radio access network (RAN) to a GAN (i.e., handover in) orfrom GAN to the PLMN's RAN (i.e., handover out). It should be recognizedthat for purposes of the present patent disclosure, the terms “GAN” or“WLAN” may be interchangeable, and may also include any UMA-based accessnetworks as well. At any rate, in order to facilitate such functionalityas well as to customize and enhance the overall user experienceassociated therewith, the present patent disclosure provides a schemewherein network information gathered by the UE device as well asinformation relating to its service options, plans, features, and thelike (more generally, “service requirements”) is transmitted to anetwork node disposed in the wireless environment 100 so that suitablenetwork-based logic is operable to respond with appropriate networkselections, lists, etc. that the UE device may use. Further, as will beseen in detail below, such network-based logic may invoke proceduresthat involve one or more correlation and filtering schemes, databasequeries, such t h a t redirection to more optimal networks may beeffectuated in the generalized network environment 100.

To formalize the teachings of the present disclosure, reference is nowtaken to FIG. 2 wherein an exemplary embodiment of a network environment200 is shown that is a more concrete subset of the generalized networkenvironment 100 illustrated in FIG. 1. As depicted, UE device 102 isoperably disposed for discovering a set of PLMNs that allow access viaconventional RAN infrastructure in addition to having connectivity withone or more GANs accessible to UE device 102. By way of example, GAN-1202-1 through GAN-N 202-N, which may be generalized for purposes of thepresent patent disclosure to also include any type of WLAN and/or I-WLANarrangements (known or heretofore unknown), are operable to bediscovered by UE device. A GAN may support connectivity to one or morePLMNS, or none at all, which can include VPLMNs 204-1 through 204-M aswell as HPLMNs (e.g., HPLMN 206) with respect to UE device 102. WhereGAN-PLMN connectivity is supported, which PLMNs behind a particular GANare visible to UE device 102 may depend on a number of commercialfactors, e.g., contractual arrangements between GAN operators and PLMNoperators. As illustrated, GAN-1 202-1 supports connectivity to VPLMN-1204-1 and VPLMN-2204-2. Likewise, GAN-2 202-1 supports connectivity toVPLMN-M 204 M as well as to HPLMN 206. On the other hand, GAN-N 202-Nhas no connectivity to the wide area PLMNS.

As is well known, each of the wide area cellular PLMNs may be arrangedas a number of cells, with each cell having sectors (e.g., typicallythree 120-degree sectors per base station (BS) or cell). Each cell maybe provided with a cell identity, which can vary depending on theunderlying WACN technology. For example, in GSM networks, eachindividual cell is provided with a Cell Global Identification (CGI)parameter to identify them. A group of cells is commonly designated as aLocation Area (LA) and may be identified by an LA Identifier (LAI).Further, at the macro level, the PLMNs may be identified in accordancewith the underlying technology. For instance, GSM-based PLMNs may beidentified by an identifier comprised of a Mobile Country Code (MCC) andMobile Network Code (MNC). Analogously, the CDMA/TDMA-based PLMNs may beidentified by a System Identification (SID) parameter. Regardless of thecellular infrastructure, all cells broadcast the macro level PLMNidentifiers such that a wireless device (e.g., UE device 102) wishing toobtain service can identify the wireless network.

FIG. 3 depicts a functional block diagram of an exemplary network system300 where a wide area cellular PLMN 306 is accessible to UE device 102through a GAN 302 a n d associated controller (GANC) 304. Essentially,in the embodiment shown, GAN 302 is operable as a broadband IP-basedaccess network providing access to the well known A/Gb interfaces ofPLMN 306, wherein GANC 300 is a network node coupled to GAN 302 via a Upreference point interface 303. As provided in applicable 3GPPspecification documents, the Up reference point 303 defines theinterface between GANC 304 and UE device 102. Where the GAN is operableto co-exist with the GSM/EDGE RAN (GERAN) infrastructure, itinterconnects to the core PLMN via the same A/Gb interfaces used by astandard GERAN Base Station Subsystem (BSS) network element.Accordingly, the functionality of GANC 304 includes necessary protocolinterworking so as to emulate the functionality of the GERAN BSS (notshown in this FIGURE). The A-interface 305 defines the interface forGSM-based circuit-switched (CS) services and is disposed between GANC304 and an MSC 308 of PLMN 306. The Gb-interface 307 defines theinterface for GPRS-based packet-switched (PS) services and is disposedbetween GANC 304 and an SGSN 310 of PLMN 306. A Security Gateway (SGW)311 may also be included in GANC 304 that is interfaced via a Wmreference point 309 (as defined by 3GPP TS 23.234) with anAuthentication, Authorization and Accounting (AAA) proxy/server node 312disposed in PLMN 306, wherein an HLR 316 is operably coupled to AAA node312. Those skilled in the art will recognize that similar infrastructuremay be deployed in a UMA-based implementation wherein a UMA networkcontroller or UNC is operable in generally in the same way as GANC 304.

In operation, GANC 304 appears to the core PLMN 306 as a GERAN BSSnetwork element by mimicking the role of the Base Station Controller(BSC) in the GERAN architecture as seen from the perspective of the A/Gbinterfaces. Accordingly, PLMN 306 to which GANC 304 is connected isunaware of the underlying access mechanism being supported by GANC,which is different from the radio access supported by the BSC. Asalluded to before, GAN 302 disposed between generic access (GA)-enabledUE device 102 and GANC 304 may be effectuated by a suitable broadband IPnetwork. The overall functionality provided by GANC 304 includes thefollowing:

-   -   User plane CS services that involve interworking CS bearers over        Up interface to CS bearers over A-interface, including        appropriate transcoding of voice to/from UE and PCM voice        from/to the MSC.    -   User plane PS services that involve interworking data transport        channels over Up interface to packet flows over Gb interface.    -   Control plane functionality including: (i) SGW for the set-up of        secure tunnel with UE for mutual authentication, encryption and        data integrity; (ii) registration for GAN service access and        providing system information; (iii) set-up of GAN bearer paths        for CS and PS services (e.g., establishment, management, and        teardown of signaling and user plane bearers between UE the        GANC); and (iv) GAN functional equivalents to GSM Radio Resource        (RR) management and GPRS Radio Link Control (RLC) such as for        paging and handovers.

FIG. 4A depicts an exemplary embodiment of a protocol stack 400Aoperable with the CS domain signaling plane associated with the networksystem 300 shown in FIG. 3. Likewise, FIG. 4B depicts an exemplaryembodiment of a protocol stack 400B operable with the PS domainsignaling plane associated with network system 300. Additional detailsregarding generic access to the A/Gb interfaces and associatedarchitecture may be found in the applicable 3GPP specificationsidentified in the U.S. provisional patent applications that have beenreferenced and incorporated hereinabove. Furthermore, to be consistentwith the broad generalization of the teachings of the present patentdisclosure, an “access network server” may comprehend a network node orelement operable to interface between the core PLMN and the UE as setforth above, which may include a GANC or a UNC as a specificimplementation.

It should be apparent to those skilled in the art that given the mosaicof various GANs/WLANs and PLMNs provided within a generalized networkenvironment such as the network environments described hereinabove withrespect to FIGS. 1 and 2, a number of GAN/GANC configurations arepossible from the perspective of providing access between a UE deviceand the available WACNs (i.e., PLMNs). FIG. 5A depicts a networkarrangement 500A where a single access network (AN) 502 is operable toconnect to a plurality of PLMNs 504-1 through 504-K according to oneembodiment, wherein each PLMN is served by a corresponding GANC. By wayof illustration, AN 502 may be generalized as a GAN which can be a WLANoperable with the GANC protocols described above, wherein a plurality ofUp interfaces 503-1 through 503-K are supported for coupling to theGANCs. Reference numerals 506-1 through 506-K refer to a plurality ofseparate GANC nodes, each for interfacing with a particular PLMNassociated therewith, wherein MSCs 508-1 through 508-K and SGSNs 510-1through 510-K are illustrative of respective PLMN's infrastructure. Oneskilled in the art should recognize that although each PLMN is providedwith a SGSN node, it is not a requirement for purposes of the presentdisclosure, and PLMNs 504-1 through 504-K may be implemented inaccordance with different wide area cellular technologies, protocols andstandards.

Referring now to FIG. 5B, depicted therein is an alternative networkarrangement 500B where AN 502 (GAN or Wireless LAN) is operable toconnect to the plurality of PLMNs 504-1 through 504-K via a singlephysical GANC 550 that supports a plurality of virtual GANC partitions552-1 through 552-K. Each virtual GANC (VGANC) is independently operableto provide the requisite A/Gb interfacing functionality with respect toa corresponding PLMN. Accordingly, there is one logical GANC per PLMNthat it connects to. Such a deployment may be used where the PLMNssupporting the WLAN connectivity do not see the need to own and operatetheir own GANC.

Based on the foregoing discussion, it should be appreciated that the GANarchitecture provides a generalized framework for interworking WLANswith 3GPP-compliant WACNs by utilizing existing protocols, e.g., GPRS,whereby little or no adaptation or standardization work is required tobe performed in the core. This allows for services to be handed overfrom a GAN/WLAN to a 3GPP-compliant WACN and vice versa, keeping thesignaling and user plane traffic intact. However, as CS-switchedprotocols and GPRS protocols (Logical Link Control or LLC andSub-Network Dependent Convergence Protocol or SNDCP) are used, theGAN/WLAN that is chosen must be able to reach an MSC/SGSN that is in thesame PLMN as the MSC/SGSN used to terminate the GAN/WLAN traffic. Tofurther complicate matters, a GAN/WLAN could connect to many PLMNs eachhaving a separate, independently discoverable GANC node as describedhereinabove. When a user encounters such a GAN/WLAN environment, thereis currently no standardized procedure to define the selection of aparticular GANC. As a consequence, a number of potential issues arisewherein the overall user experience as well as call handover behaviormay be negatively impacted. For instance, if a GA-compliant UE devicethat operates in dual mode (i.e., two different technologies, eachpreferably in a separate band, for example) discovers a macro PLMN orWACN and subsequently chooses a GANC that belongs to a different WACN,handover between the AN and WACN spaces would not work. Such issues mayalso arise in network arrangements where a single GANC is partitioned tosupport a number of independently discoverable VGANC partitions.

Further, because of various levels of technology penetration anddeployment in different regions and countries, additional complexitiescan arise where the AN and WACN spaces are to be interfaced using theGAN/WLAN approach. For example, a GA-compliant UE device may find itselfin an area where there is no WACN coverage but there is WLAN coverage.If one or more WLANs are based on the I-WLAN approach rather than theGAN architecture, it is preferable that the UE differentiate between GANand I-WLAN due to the differences in various control processes, e.g.,registration, de-registration, etc., in addition to whatever servicedifferences that may exist between them. For purposes of highlightingthe scope of the present patent disclosure, some of the userexperience-related issues are set forth below.

-   -   The UE is not currently registered on a WACN. Here the UE cannot        check the cellular band signals to determine the country it is        in (i.e., MCC is unknown) to select the best or optimal        provider. Although HPLMN is usually selected first, VPLMN        preference may depend on location (e.g., country). In this        situation, the UE may not know which VPLMN it prefers to connect        to when it is examining the available GAN/WLANs.    -   The operator's “Preferred PLMN” list on the Subscriber Identity        Module (SIM) or Removable user Identity Module (RUIM) associated        with the user does not take into account the UE's need for PS        data services (e.g., GPRS capability) or other services such as        Unlicensed Mobile Access (UMA) services. Such a situation may        arise where the PLMN list is based only on CS voice roaming        agreements and, as a result, the user may not be able to use        email and other data services. One skilled in the art will note        that such an issue can arise whether or not GAN or I-WLAN is        used.    -   Some or all of the operator-controlled lists for PLMNs may not        be up-to-date, or particular entries for the country the UE is        operating in may not be current.    -   Because it takes up capacity to update lists over the cellular        band, the HPLMN may wish to update lists during off-hours or        when the UE is connected over I-WLAN or GAN.    -   When there are no WACN signals to allow the UE to determine the        MCC, the availability of AGPS (Assisted Global Positioning        System) in the UE, or a (manual) user input, as well as recent        (i.e., time-stamped) information on WACN MCC may be helpful.    -   The case of operation close to country border(s) may result in        the UE obtaining signals from more than one MCC, enabling user        choice or “least cost” choice.

Those skilled in the art should recognize that the list set forth aboveis purely illustrative rather than limiting. It is envisaged that uponreference hereto various related problems may become apparent withrespect to user experience and call behavior in the context ofinterfacing between GAN/WLAN and PLMN spaces.

For purposes of the present disclosure, the GA-capable UE may operate ineither Automatic or Manual mode with certain differences in networkdiscovery and selection procedures, although the particular features andcapabilities of the two may vary depending on the applicablespecification(s) as well as any modifications and changes that may bemade to them. In general, the Manual mode allows the user to do moredetailed selection/filtering of the available PLMNs, the bearer(s) to beused, and potentially even of the method to be used when using WLAN orother unlicensed radio technology (i.e., I-WLAN, GAN, or just aconnection through the WLAN to the PLMN). Additional details regardingnetwork discovery and selection may be found in one or more of theabove-referenced U.S. provisional patent application(s) andnonprovisional patent application(s).

Referring now to FIG. 6, shown therein is a flowchart of a generalizednetwork discovery and selection scheme according to one embodimentwherein a UE device is disposed in a network environment comprising aGAN/WLAN space as well as a WACN space. As illustrated, the flowchart ofFIG. 6 captures a methodology where the UE device gathers appropriatenetwork information upon power-up and initial discovery (as perapplicable 3GPP-compliant procedures), which is then transmitted to anetwork node for determining a more optimal network arrangement (i.e.,appropriate GANC+PLMN combination), preferably in view of the UEdevice's service requirements that may also be advertised to the networknode. Accordingly, by effectuating appropriate resolution ofUE-discovered network information and its service requirements, thenetwork node is amenable to provide suitable instructions to the UEdevice for obtaining better service instantiation, which may includeredirection to more suitable networks, location-based filtering, and thelike.

Continuing to refer to FIG. 6, at block 602, the UE device gathersnetwork information via scanning relative to one or more WACNtechnologies, bands, and frequencies. Additionally or alternatively, theUE device is also adapted to gather network information via scanningrelative to one or more GAN/WLAN technologies, bands, and frequencies(block 604). Thereafter, the UE device transmits the gathered networkinformation as well as service/feature requirements (e.g., voice-onlyservices, data-only services, voice-and-data services, GAN services,handover services, UMA services capability, calling plans associatedwith the UE device, and/or location area information associated with theUE device, et cetera) to a network node (block 606). In one embodiment,the gathered network information may comprise at least one of cellidentity information of a WACN on which the UE device is registered(i.e., CGI information of a registered GSM/GERAN), CGI/cell IDinformation relating to other available wide area cellular networks,cause values of any prior registration failures, Broadcast ControlChannel (BCCH) information of at least one available wide area cellularnetwork, and Packet Control Channel (PCCH) information of at least oneavailable wide area cellular network. As alluded to hereinabove, in oneembodiment, WACNs may be identified by their {MCC, MNC} combinations.Also, additional features such as identifying whether a particular WACNis data-capable (e.g., GPRS-capable) may also be provided. To the extentthe UE device is adapted to operate based on various network lists,stored or otherwise, additional selection criteria and filters such asForbidden GAN/PLMN lists, Priority GAN/PLMN lists (which may be stored,for example, in a Subscriber Identity Module (SIM) or Removable userIdentity Module (RUIM), or in a device memory) and the like, may also beprovided to the network node. In a further implementation, the UE couldalso list PLMNs that only provide WACN and/or WAN coverage.

It should be realized that scanning operations set forth above may beperformed via active scanning or passive scanning methods. Also, theremay be more than one band operable with GANs and/or with PLMNs. In oneinstance, a frequency band may be selected from the group comprising 450MHz, 850 MHz, 900 MHz, 1800 MHz, 1700 MHz, 1900 MHz, 2100 MHz, 2700 MHz,or other frequencies and/or any satellite bands.

Upon receiving the gathered network information, service requirementinformation and/or location information from the UE device, the servicelogic associated with the network node is operable to resolve theservice requirements requested by the UE device in view of the otherbodies of the received information so that a determination may be madeas to whether additional or alternative network arrangements areavailable for the UE device. In some implementations, such resolutionmay involve interfacing with additional network nodes and databases(e.g., HPLMN and/or home GANC, service databases, roaming databases, andso on). Thereafter, appropriate instructions may be provided via asuitable response message to the UE device, including pertinentinformation relative to any additional or alternative networkarrangements. These operations are illustrated in block 608. Based onthe instructions received from the network node, the UE device may thenengage in obtaining appropriate service, which can sometimes warrantnetwork redirection (block 610).

FIGS. 7A and 7B depict flowcharts of exemplary scenarios of the networkinformation collection process set forth above. Presently, applicableGAN specifications state that a UE device, e.g., a mobile station (MS),shall first register on a GSM/GERAN PLMN if found and allowed accordingto current 3GPP network selection procedures. Accordingly, the processflow exemplified in FIG. 7A begins with scanning available bands forGERAN PLMN networks (block 702). For each GERAN PLMN found, informationis obtained and stored (blocks 704, 706 and 708), e.g., CGI information,BCCH and/or PCCH information, etc. The UE device then selects andregisters on a GERAN PLMN (block 710) according to 3GPP specifications,which may be mediated by the UE device's network lists, preferences, andother filters. If the registration with a particular PLMN fails, thereason for failure is stored as a cause value (blocks 712 and 714). Oncethe reason for failure is stored, the registration process may repeatwith respect to the additional PLMNs discovered according to 3GPPspecifications (block 716). On the other hand, if the PLMN registrationis successful or if registration with no PLMN has been successful andthe UE device is allowed to operate in GAN-only mode, further processflow may accordingly follow (block 718). However, if the PLMNregistration is successful but that PLMN does not support GANconnectivity, various concerns might arise that could negatively impactthe service selection behavior of the UE device.

With respect to operating in GAN-mode, the UE device is operable toprovide a number of information elements to a GANC node with which itestablishes initial connectivity. Preferably, as pointed out in theforegoing discussion, such information can include network informationgathered via scanning in other bands or modes as well as servicerequirements. Referring to FIG. 7B in particular, upon successfulregistration a PLMN or failure to register on any PLMN (block 750), theUE device is operable to search for a GAN network (block 752),preferably according to applicable 3GPP specifications. Once a UniformResource Locator (URL) or IP address of a GANC node has been obtained(block 754), the UE device authenticates and registers with the GANCusing, for instance, known Generic Access—Resource Control (GA-RC)REGISTER REQUEST messaging (block 756). Alternatively, where a defaultGANC's information is stored in the UE device, such information may beutilized in initiating registration. Typically, GANC information iscomprised of a GANC Security Gateway (SGW) address, a GANC address and aGANC TCP port number. The IP address of the SGW may be locally stored inthe UE device, or if the device is provided with a Fully QualifiedDomain Name (FQDN), a DNS query may be performed to obtain the IPaddress. In accordance with the discussion set forth in the foregoingsections, such a registration message to the GANC may includeinformation elements pertaining to any of the following in anycombination:

-   -   registered GERAN CGI information if available;    -   if the registration is for voice and/or data;    -   services and features requested by the UE device, e.g.,        voice-only services, data-only services, voice-and-data        services, GAN services, multimedia services, value-added        services, etc.;    -   if handover is required;    -   if home-country-calls-only calls are required;    -   prior GERAN PLMN registration attempts and associated cause        values for failure;    -   the registration request may also include GERAN PLMN information        for which registration was successful but a GANC redirect was        received. Any VPLMN information identified therein may be marked        as such (described in detail hereinbelow);    -   CGI information for other PLMNs available; and    -   BCCH/PCCH information for available PLMNs. For instance, in one        implementation, BCCH/PCCH information for all available PLMNs is        included. In other implementations, BCCH/PCCH information for a        portion of available PLMNs may be included.        Further, upon successful authentication and registration with        the GANC, additional network information may be collected by the        UE device (e.g., appropriate network arrangement via a suitable        response message), as illustrated in block 758.

In addition to the various information elements described above withrespect to an exemplary registration request, other information elementspertaining to location and/or identification may also be included. Byway of illustration, such location and identification information mayinclude:

A. Cellular/WACN

1. MCC

-   -   a. Cellular MCC (e.g., GSM)    -   b. Country code associated with a microcell (or even a small        macrocell) on a vehicle (e.g., ships, planes, trains, buses,        etc.)

2. MNC

3. LAI

4. CGI, etc.

5. Network generated information such as current cell (and sector)

6. Geolocation based on network information, of varying degrees ofaccuracy

7. Geolocation based on handset assisted GPS or other positioning system

B. WLAN/GAN

-   -   Service Set ID (SSID)    -   Other

C. Manual input information and other information

-   -   1. AP building and floor and room location and similar        descriptive information.    -   2. AP information based on location information derived from        dual mode handsets, where the location of the handset is then        transferred to a database to provide some (perhaps gross or        rough) information on the location of the AP. Could be        geographic information or could indicate the LAI or CGI of        cellular systems.    -   3. AP information, as in (2), but derived from recent        information from the handset, e.g., the cell and network that        the handset was viewing a few minutes ago before the user walked        into a building and lost coverage. The time between loss of        cellular or other information and the connection to the access        point is a means of further identifying the potential lack of        accuracy of the information.    -   4. Indication of the type of AP.        -   a. small, potentially easily moved        -   b. fixed in place (at least initially)        -   c. mobile, as on a ship or in a plane or on a train—there            may be specific types of country codes when the devices in            part of a vehicle    -   5. Whether the connectivity of the AP has changed.    -   6. Location (GPS or other, even manual entry) of the ship, plane        or vehicle with an AP or microcell.

It should be realized by those skilled in the art that the locationinformation may be developed by one element (i.e., a UE device) andstored in another element (AP, or microcell or base station controlleror GANC), or even in a “universal” database within a PLMN or operator.Further, it should be recognized that location of an AP and its relationto the elements of other (even competing) networks is useful for manypurposes, such as assisting in handover (or similar) transition of thehandset connectivity, which may include “roving” as defined in 3GPPdocumentation. By way of illustration, exemplary uses of location andidentification information include:

-   -   Identification of the operator and/or PLMN or otherwise defined        network    -   Identification of relationship with an operator or PLMN or        otherwise defined network    -   Identification of location        -   a. For E911 and public safety purposes        -   b. Including passing of information to the PSAP (Public            Safety Answer Point)        -   C. For commercial purposes        -   Operation of a cellular network or of an unlicensed network.

Based on the foregoing, it will be realized that the registrationprocedure may be initiated towards a default AN node (e.g., a GANC or aUNC) after a successful discovery procedure or after a failedregistration towards a serving AN node, where no GAN PLMN list wasprovided to the UE from the default AN node. Further, the registrationprocedure may also be initiated towards the default AN node when noadditional PLMNs can be selected from the GAN PLMN list received fromthe default AN node. Additionally, the registration procedure may betriggered towards the default AN node where the UE wishes to performmanual PLMN selection. If the UE is already successfully registered witha serving AN node and a manual PLMN selection is initiated, the UE firstderegisters from the current serving AN node and then initiatesregistration towards the default AN node. In this embodiment, theregistration request may also include an indication that a list of PLMNidentities is requested for manual selection.

Additional operations and/or information elements may be involved if theregistration processes take place after the initial network discoveryand registration process by the UE device as set forth above. Forinstance, with respect to WACN space (e.g., GERAN), if the UE devicereceives a redirect message from a GANC node (which could be a separatemessage or part of a general redirect message), the UE device mayderegister from the current serving GERAN VPLMN and attempt registrationon the VPLMNs in a number of ways. By way of illustration, the VPLMNsmay be provided by the GANC in some priority order that may be followedby the UE device. Alternatively, if no order has been provided, a VPLMNmay be chosen from the supplied list at random. With respect tosubsequent registrations in GAN space, if the UE device has beenredirected to another VPLMN and registration with that new VPLMN issuccessful, the UE device may be required to re-register with the homeGANC using the same GAN as before. Alternatively, the UE device mayregister with the GANC associated with the new VPLMN if that informationhas been made available by the redirecting GANC. In a still furthervariation, there may be no subsequent GANC registration pursuant toinstructions from the GANC.

Given the interfacing between the WACN and GAN spaces as described inthe foregoing sections, selecting a proper PLMN and GANC combinationthat allows optimal service may be modulated based on a number offactors, e.g., service requirements, available network information,service capabilities, location information, and the like. When a servingnetwork node (e.g., a default GANC or a provisioning GANC) receivesappropriate information from the UE device, at least part of the servicelogic involves resolving whether a home GANC or a GANC associated with aVPLMN should provide service to the UE device. FIGS. 8A and 8B are twoflowcharts associated with GANC selection and optional redirection inaccordance with an embodiment of the present patent disclosure. When theserving network node receives information from a UE device (block 802),the service logic associated with the node determines (i) if local homenetwork calls are required; and/or (ii) if handover is not required andno VPLMN GANC can be used (block 804). If so, the network node providesinstructions to the UE device to select a home network GANC (block 806).On the other hand, based on the received information from the UE device(block 820), the network node service logic determines (i) handover ofservices is required; and/or (ii) VPLMN dialing plan is required (block822). In that case, the network node provides instructions to the UEdevice to select a VPLMN-associated GANC (block 824).

It should be apparent that the service logic is preferably operable toevaluate and resolve a number of service scenarios based on thecombinations of service and feature requirements as well as the networkinformation received from the UE device. Additional details andflowcharts regarding exemplary service scenarios that can includeredirection may be found in one or more of the above-referenced U.S.provisional patent application(s) and nonprovisional patentapplication(s), which are incorporated by reference.

Referring now to FIG. 9, shown therein is a functional block diagram ofan exemplary AN server node 900, e.g., GANC/UNC node 900 according toone embodiment. Those skilled in the art should appreciate that ANserver node 900 may be provided in any of the configurations depicted inFIGS. 5A and 5B described hereinabove. Regardless, AN server node 900includes appropriate network selection logic 902 operable to perform oneor more of the procedures set forth above with respect to resolvinggathered network information and service/feature requirement informationthat is provided by a UE device. Accordingly, in one embodiment,suitable storage areas may be provided for storing service/featurerequirements 904 as well as gathered network information 906. Databasequery logic 908 is provided to facilitate database query andinterrogation of local and/or remote databases, e.g., DB 910-1 throughDB 910-N.

FIG. 10 depicts a block diagram of an embodiment of a UE device operableaccording to the teachings of the present patent disclosure. It will berecognized by those skilled in the art upon reference hereto thatalthough an embodiment of UE 102 may comprise an arrangement similar toone shown in FIG. 10, there can be a number of variations andmodifications, in hardware, software or firmware, with respect to thevarious modules depicted. Accordingly, the arrangement of FIG. 10 shouldbe taken as illustrative rather than limiting with respect to theembodiments of the present patent disclosure. A microprocessor 1002providing for the overall control of an embodiment of UE 102 is operablycoupled to a communication subsystem 1004 which includestransmitter/receiver (transceiver) functionality for effectuatingmulti-mode communications over a plurality of bands. By way of example,a wide area wireless Tx/Rx module 1006, a GAN Tx/Rx module 1008 and anI-WLAN Tx/Rx module 1010 are illustrated. Although not particularlyshown, each Tx/Rx module may include other associated components such asone or more local oscillator (LO) modules, RF switches, RF bandpassfilters, A/D and D/A converters, processing modules such as digitalsignal processors (DSPs), local memory, etc. As will be apparent tothose skilled in the field of communications, the particular design ofthe communication subsystem 1004 may be dependent upon thecommunications networks with which the UE device is intended to operate.In one embodiment, the communication subsystem 1004 is operable withboth voice and data communications.

Microprocessor 1002 also interfaces with further device subsystems suchas auxiliary input/output (I/O) 1018, serial port 1020, display 1022,keyboard 1024, speaker 1026, microphone 1028, random access memory (RAM)1030, a short-range communications subsystem 1032, and any other devicesubsystems generally labeled as reference numeral 1033. To controlaccess, a SIM/RUIM interface 1034 is also provided in communication withthe microprocessor 1002. In one implementation, SIM/RUIM interface 1034is operable with a SIM/RUIM card having a number of key configurations1044 and other information 1046 such as identification andsubscriber-related data as well as one or more PLMN and SSID lists andfilters alluded to hereinabove.

Operating system software and other control software may be embodied ina persistent storage module (i.e., non-volatile storage) such as Flashmemory 1035. In one implementation, Flash memory 1035 may be segregatedinto different areas, e.g., storage area for computer programs 1036 aswell as data storage regions such as device state 1037, address book1039, other personal information manager (PIM) data 1041, and other datastorage areas generally labeled as reference numeral 1043, whereinappropriate GANC or UNC information may be stored according to oneimplementation. Additionally, appropriate network discovery/selectionlogic 1040 may be provided as part of the persistent storage forexecuting the various procedures, correlation techniques,service/feature requirement selection and identification processes aswell as GANC selection mechanisms set forth in the preceding sections.Associated therewith is a storage module 1038 for storing the SSID/PLMNlists, selection/scanning filters, capability indicators, et cetera,also alluded to hereinabove.

Based on the foregoing, it should be clear that the UE device logic andhardware includes at least the following: a logic module and/orassociated means for gaining IP connectivity with respect to a wirelessaccess network node disposed in a network environment that is comprisedof a wireless AN space operable to be coupled to a WACN space; and alogic module and/or associated means for initiating a registrationrequest message towards the wireless access network node, wherein theregistration request message includes at least one information elementpertaining to AN services required by the UE device.

It is believed that the operation and construction of the embodiments ofthe present patent disclosure will be apparent from the DetailedDescription set forth above. While the exemplary embodiments shown anddescribed may have been characterized as being preferred, it should bereadily understood that various changes and modifications could be madetherein without departing from the scope of the present invention as setforth in the following claims.

1. A network messaging method, comprising: gaining Internet Protocol(IP) connectivity by a user equipment (UE) device with respect to awireless access network node disposed in a network environment that iscomprised of a wireless access network (AN) space operable to be coupledto a wide area cellular network (WACN) space; and initiating aregistration request message by said UE device towards said wirelessaccess network node, wherein said registration request message includesat least one information element pertaining to AN services required bysaid UE device.
 2. The network messaging method as recited in claim 1,wherein said wireless access network node comprises a generic accessnetwork controller (GANC).
 3. The network messaging method as recited inclaim 2, wherein said GANC is a default GANC whose information is storedin said UE device.
 4. The network messaging method as recited in claim1, wherein said wireless access network node comprises an UnlicensedMobile Access (UMA) network controller (UNC).
 5. The network messagingmethod as recited in claim 4, wherein said UNC is a default UNC whoseinformation is stored in said UE device.
 6. The network messaging methodas recited in claim 1, wherein said registration request message isinitiated towards said wireless access network node after a successfuldiscovery procedure.
 7. The network messaging method as recited in claim1, wherein said registration request message is initiated towards saidwireless access network node after a failed registration with a servingaccess network node.
 8. A user equipment (UE) device, comprising: meansfor gaining Internet Protocol (IP) connectivity with respect to awireless access network node disposed in a network environment that iscomprised of a wireless access network (AN) space operable to be coupledto a wide area cellular network (WACN) space; and means for initiating aregistration request message towards said wireless access network node,wherein said registration request message includes at least oneinformation element pertaining to AN services required by said UEdevice.
 9. The UE device as recited in claim 8, wherein said wirelessaccess network node comprises a generic access network controller(GANC).
 10. The UE device as recited in claim 9, wherein said GANC is adefault GANC whose information is stored in said UE device.
 11. The UEdevice as recited in claim 8, wherein said wireless access network nodecomprises an Unlicensed Mobile Access (UMA) network controller (UNC).12. The UE device as recited in claim 11, wherein said UNC is a defaultUNC whose information is stored in said UE device.
 13. The UE device asrecited in claim 8, wherein said registration request message isinitiated towards said wireless access network node after a successfuldiscovery procedure.
 14. The UE device as recited in claim 8, whereinsaid registration request message is initiated towards said wirelessaccess network node after a failed registration towards a serving accessnetwork node.
 15. The UE device as recited in claim 8, further includesmeans for storing an IP address in said UE device, said IP address foridentifying said wireless access network node.
 16. The UE device asrecited in claim 8, further includes means for storing a Fully QualifiedDomain Name (FQDN) in said UE device, said FQDN for facilitating aDomain Name Query (DNS) with respect to an IP address of said wirelessaccess network node.
 17. A network system, comprising: a wireless accessnetwork node disposed in a network environment that is comprised of awireless access network (AN) space operable to be coupled to a wide areacellular network (WACN) space, said wireless access network node forfacilitating wireless access services with respect to a Public LandMobile Network (PLMN) of said WACN space; a user equipment (UE) deviceincluding means for gaining Internet Protocol (IP) connectivity withsaid wireless access network node; and means associated with said UEdevice for initiating a registration request message towards saidwireless access network node, wherein said registration request messageincludes at least one information element pertaining to wireless accessservices required by said UE device.
 18. The network system as recitedin claim 17, wherein said wireless access network node comprises ageneric access network controller (GANC).
 19. The network system asrecited in claim 18, wherein said GANC is a default GANC whoseinformation is stored in said UE device.
 20. The network system asrecited in claim 17, wherein said wireless access network node comprisesan Unlicensed Mobile Access (UMA) network controller (UNC).
 21. Thenetwork system as recited in claim 20, wherein said UNC is a default UNCwhose information is stored in said UE device.
 22. The network system asrecited in claim 17, wherein said registration request message isinitiated towards said wireless access network node after a successfuldiscovery procedure.
 23. The network system as recited in claim 17,wherein said registration request message is initiated towards saidwireless access network node after a failed registration towards aserving access network node.
 24. The network system as recited in claim17, wherein said means for gaining IP connectivity is operableresponsive to an IP address stored in said UE device, said IP addressfor identifying said wireless access network node.
 25. The networksystem as recited in claim 17, wherein said means for gaining IPconnectivity is operable responsive to a Fully Qualified Domain Name(FQDN) stored in said UE device, said FQDN for facilitating a DomainName Query (DNS) with respect to an IP address of said wireless accessnetwork node.